8.1
HIGH CVSS 3.1
CVE-2026-28387
Potential Use-after-free in DANE Client Code
Description

Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side. Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage. By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable. The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records. No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary.

INFO

Published Date :

April 7, 2026, 10:16 p.m.

Last Modified :

April 23, 2026, 3:39 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-28387 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Openssl openssl
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 HIGH [email protected]
Solution
Update client software to fix a use-after-free vulnerability related to DANE TLSA authentication.
  • Update client software to the latest version.
  • Ensure TLSA record configurations are verified.
  • Avoid non-standard TLSA record usages.
Public PoC/Exploit Available at Github

CVE-2026-28387 has a 3 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-28387 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-28387 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

None

Updated: 20 hours, 55 minutes ago
0 stars 0 fork 0 watcher
Born at : April 28, 2026, 11:23 a.m. This repo has been linked 6 different CVEs too.

trivy-nginx-scan

Updated: 2 weeks ago
0 stars 0 fork 0 watcher
Born at : April 14, 2026, 1:37 p.m. This repo has been linked 106 different CVEs too.

All Public RunWhen Helm Charts - Managed by terraform

Shell Dockerfile Go Template

Updated: 4 days, 22 hours ago
1 stars 0 fork 0 watcher
Born at : Sept. 18, 2023, 10:09 a.m. This repo has been linked 115 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-28387 vulnerability anywhere in the article.

  • TheCyberThrone
OpenSSL 3.6.2: The Moderate Severity Wave

OpenSSL 3.6.2 landed this week carrying eight CVE fixes, with the project rating the most severe issue as Moderate. On the surface, that sounds reassuring—no critical exploits, no ransomware-grade zer ... Read more

Published Date: Apr 08, 2026 (2 weeks, 6 days ago)
  • CybersecurityNews
Multiple OpenSSL Vulnerabilities Exposes Sensitive Data in RSA KEM Handling

OpenSSL has released a broad April 2026 security update that fixes seven vulnerabilities across supported branches, led by CVE-2026-31790, a moderate-severity flaw in RSA KEM RSASVE encapsulation that ... Read more

Published Date: Apr 08, 2026 (3 weeks ago)
  • Help Net Security
OpenSSL 3.6.2 lands with eight CVE fixes

OpenSSL 3.6.2 patches eight CVEs across a range of components. The project rates the most severe issue in the release as Moderate. What got fixed The release fixes incorrect failure handling in RSA KE ... Read more

Published Date: Apr 08, 2026 (3 weeks ago)
  • Daily CyberSecurity
OpenSSL Issues Major Security Advisory: RSA and Memory Vulnerabilities Fixed

OpenSSL has released a comprehensive security advisory detailing seven vulnerabilities ranging from Moderate to Low severity. The report, dated April 7, 2026, highlights critical fixes for modern vers ... Read more

Published Date: Apr 08, 2026 (3 weeks ago)

The following table lists the changes that have been made to the CVE-2026-28387 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Apr. 23, 2026

    Action Type Old Value New Value
    Added CVSS V3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
    Added CPE Configuration OR *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.0.0 up to (excluding) 3.0.20 *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.3.0 up to (excluding) 3.3.7 *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.4.0 up to (excluding) 3.4.5 *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.5.0 up to (excluding) 3.5.6 *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.6.0 up to (excluding) 3.6.2 *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 1.1.1 up to (excluding) 1.1.1zg
    Added Reference Type OpenSSL Software Foundation: https://github.com/openssl/openssl/commit/07e727d304746edb49a98ee8f6ab00256e1f012b Types: Patch
    Added Reference Type OpenSSL Software Foundation: https://github.com/openssl/openssl/commit/258a8f63b26995ba357f4326da00e19e29c6acbe Types: Patch
    Added Reference Type OpenSSL Software Foundation: https://github.com/openssl/openssl/commit/444958deaf450aea819171f97ae69eaedede42c3 Types: Patch
    Added Reference Type OpenSSL Software Foundation: https://github.com/openssl/openssl/commit/7a4e08cee62a728d32e60b0de89e6764339df0a7 Types: Patch
    Added Reference Type OpenSSL Software Foundation: https://github.com/openssl/openssl/commit/ec03fa050b3346997ed9c5fef3d0e16ad7db8177 Types: Patch
    Added Reference Type OpenSSL Software Foundation: https://openssl-library.org/news/secadv/20260407.txt Types: Vendor Advisory
  • New CVE Received by [email protected]

    Apr. 07, 2026

    Action Type Old Value New Value
    Added Description Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side. Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage. By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable. The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records. No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary.
    Added CWE CWE-416
    Added Reference https://github.com/openssl/openssl/commit/07e727d304746edb49a98ee8f6ab00256e1f012b
    Added Reference https://github.com/openssl/openssl/commit/258a8f63b26995ba357f4326da00e19e29c6acbe
    Added Reference https://github.com/openssl/openssl/commit/444958deaf450aea819171f97ae69eaedede42c3
    Added Reference https://github.com/openssl/openssl/commit/7a4e08cee62a728d32e60b0de89e6764339df0a7
    Added Reference https://github.com/openssl/openssl/commit/ec03fa050b3346997ed9c5fef3d0e16ad7db8177
    Added Reference https://openssl-library.org/news/secadv/20260407.txt
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.